Release 10.1A: OpenEdge Application Server:
Developing WebSpeed Applications

Using the <!--WSTAG--> custom tag

This is the default definition for the <!--WSTAG --> tag installed in tagmap.dat:

!--WSTAG,,,fill-in,web/support/tagrun.p

This is a good example of how you might define your own custom tags. At Web object generation time, the Progress® WebSpeed® Workshop associates the <!--WSTAG --> custom tag with a SpeedScript fill-in field. That is, a local variable (fill-in) appears in the Web object after an HTML file (that contains <!--WSTAG -->) has been opened and saved as a new Web object.

As with the other utility procedures in WebSpeed, at run-time, tagrun.p is run in combination with a few other procedures to dynamically generate an HTML table.

To use the <!--WSTAG --> custom tag in an HTML file, you must specify the NAME and FILE attributes in order to generate a table or other custom HTML output.

NAME attribute

As with other HTML fields, the NAME attribute’s value is used as the associated WebSpeed object name and label in the Web object. In the case of <!--WSTAG -->, the associated WebSpeed object is a fill-in field.

FILE attribute

The FILE attribute in <!--WSTAG --> provides the name of the SpeedScript procedure that generates the HTML. If FILE is set to a filename, tagrun.p runs the specified file as a SpeedScript procedure. If FILE is set to "screenvalue", tagrun.p retrieves the value of the SpeedScript SCREEN-VALUE attribute on the fill-in field associated with <!--WSTAG --> and uses this value as the name of the SpeedScript procedure to run.

These are examples of the three techniques, where tagrun.p runs the SpeedScript procedure mytbl.p and then runs the file specified by the value of the associated fill-in field:

<!--WSTAG NAME=mytbl FILE=mytbl.p --> <!--WSTAG NAME=mytbl FILE=screenvalue --> <!--WSTAG NAME=mytbl -->

With the third example, you must create a custom web.output control handler in Workshop and generate the table directly.